Skip to content

AP-613 convert oclc number to int if it's a float in the spreadsheet#7

Open
davezuckerman wants to merge 1 commit intomainfrom
AP-613-float-ruby-noko-upgrade
Open

AP-613 convert oclc number to int if it's a float in the spreadsheet#7
davezuckerman wants to merge 1 commit intomainfrom
AP-613-float-ruby-noko-upgrade

Conversation

@davezuckerman
Copy link

  • Bumped ruby version to 3.3

  • Bumped rubocop to 1.75

  • Bumped nokogiri to 1.19.1

  • Converts oclc number to an integer if it's a float in the spreadsheet

converting oclc numbers to floats in spec

removed spaces at end of line for rubocop

bumped nokogiri to 1.19 and ruby to 3.3

forgot to update the build and gem push files with the updated ruby version

updated rubocop target to ruby 3.3

bumped rubocop version
Copy link
Member

@awilfox awilfox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good. One minor typo, and a question on Rubocop version pinning, then r+.

return to_enum(:each_oclc_number) unless block_given?

ss.each_value(oclc_col_index, include_header: false) do |v|
# convert to integer if oclc number is a float in the spreadsheet"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# convert to integer if oclc number is a float in the spreadsheet"
# convert to integer if oclc number is a float in the spreadsheet

spec.add_development_dependency 'rake', '~> 13.0'
spec.add_development_dependency 'rspec', '~> 3.10'
spec.add_development_dependency 'rubocop', '= 1.39'
spec.add_development_dependency 'rubocop', '~> 1.75'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to ~> 1.75? This will automatically pull in newer versions (and potentially change reports/passes) whenever dependencies are updated. We did ~> 1.84.0 in UCBEARS and ~> 1.77.0 in Framework; should this be ~> 1.75.0 instead?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants